In the forecast, everything is displayed per month, but the data is the same as staffing. While the forecast-data itself comes from the backend and will be transformed there, the data used for the infopills and the hovered state where we show which project the hours derive from must be transformed as well. We decided to do this in the frontend, and I have made a class dedicated to transforming the data, as well as a converter, converting week numbers into months, with data on the distribution of months if a week happens to be in two months.
I was hoping to be able to reuse some of the files that were used in staffing, but because of the weektypes used everywhere I had to create copys where there are not many differences, mostly the word week is replaced by the word month and the data is transformed as needed.

The data is still only testdata, and so the bookingmodel and detailedbooking does not necessarily correspond with each other, so the values do not make so much sense.